Download Oracle WebLogic Server 12c: Advanced Administrator II.1z0-134.Prep4Sure.2017-12-01.44q.vcex

C: A callback handler used to control the failover and failback within a multi data source must include an implementation of the weblogic.jdbc.extensions.ConnectionPoolFailoverCallback interface. D: You can register a callback handler with WebLogic Server that controls when a multi data source with the Failover algorithm fails over connection requests from one JDBC data source in the multi data source to the next data source in the list. Incorrect Answers:B: Frequency of these tests is controlled by the Test Frequency Seconds attribute of the multi source. The default value for Test Frequency is 120 seconds, so if you do not specifically set a value for the option, the multi data source will test disabled data sources every 120 seconds. Reference: http://docs.oracle.com/cd/E23943_01/web.1111/e13737/jdbc_multidatasources.htm#JDBCA223

You can find help on Client ID Policy configuration through the following path: OTN Home > Oracle WebLogic Server 12.1.1.0 Documentation > Administration Console Online Help > JMS Connection Factory: Configuration: ClientReference: http://docs.oracle.com/cd/E24329_01/apirefs.1211/e24401/pagehelp/JMSjmsconnectionjmsconnectionfactoryconfigclientparamstitle.html

By default, the rotated files are stored in the same directory where the log file is stored. The server log file is located on the computer that hosts the server instance. By default, the server log file is located below the server instance's root directory: root-directory\server-name\server-name.log. https://docs.oracle.com/cd/E28280_01/web.1111/e13739/config_logs.htm#WLLOG139

When using automatic service migration, the Node Manager is required to get health monitoring information about the member servers involved, as follows:* Consensus leasing – Node Manager must be running on every machine hosting managed servers within the cluster. * Database leasing – Node Manager must be running on every machine hosting managed servers within the cluster only if pre/post-migration scripts are defined. If pre/post-migrations are not defined, then Node manager is not required. Reference: https://docs.oracle.com/cd/E13222_01/wls/docs103/cluster/service_migration.html

One server instance in a cluster that contains migratable servers acts as the cluster master and orchestrates the process of automatic server migration, in the event of failure.  Any Managed Server in a cluster can serve as the cluster master, whether it hosts pinned services or not. Note: Any server instance in the cluster can serve as the cluster master. When you start a cluster that contains migratable servers, the first server to join the cluster becomes the cluster master and starts up the cluster manager service. If a cluster does not include at least one migratable server, it does not require a cluster master, and the cluster master service does not start up. Reference: https://docs.oracle.com/cd/E12839_01/web.1111/e13709/migration.htm#CLUST285

With CLIENT_ACKNOWLEDGE the Session object relies on the application to call an acknowledge method on a received message. Once the method is called, the session acknowledges all messages received since the last acknowledge. Incorrect Answers:A: With CLIENT_ACKNOWLEDGE the Session object acknowledges receipt of a message once the receiving application method has returned from processing it.C: With DUPS_OK_ACKNOWLEDGE the Session object acknowledges receipt of a message once the receiving application method has returned from processing it;duplicate acknowledges are permitted. D: There is no acknowledge mode named DEFAULT_ACKNOWLEDGE.Reference: http://docs.oracle.com/cd/E12840_01/wls/docs103/jms/fund.html

This thread is considered Stuck by WebLogic because it's been running for over the time defined in MaxStuckThreadTime (600 seconds by default). Weblogic Server waits for this time to be reached before marking a thread as stuck if the thread is still working after this time. Example: [STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' id=73 idx=0x128 nid=13410 prio=1 alive, in native, daemonReference: https://blogs.oracle.com/WebLogicServer/entry/analyzing_a_stuck_weblogic_execute

A: Before you begin the upgrade process, make sure that you take any necessary precautions such as:* Back up your applications, database schema, other application data, and domains. * If required, obtain latest third party plug-ins or components that are compatible with required non-Oracle components. For example, Apache Web Server libraries. CGED: The rolling upgrade process includes stopping the Administration Server, installing the upgrade, restarting the Administration Server, and then doing the same for each Managed Server in the cluster (machine). Reference: http://docs.oracle.com/cd/E14571_01/web.1111/e13754/rolling_upgrade.htm#WLUPG268

A connection factory supports concurrent use, enabling multiple threads to access the object simultaneously. A session and its message producers and consumers can only be accessed by one thread at a time (i.e. the access must be synchronized). Their behavior is undefined if multiple threads access them simultaneously. Incorrect Answers:A, E: A connection factory supports concurrent use, enabling multiple threads to access the object simultaneously.C, D: A session and its message producers and consumers can only be accessed by one thread at a time. Their behavior is undefined if multiple threads access them simultaneously. Reference: http://docs.oracle.com/cd/E12840_01/wls/docs103/jms/fund.html

Incorrect Answers:A, B: JMS supports two messaging models: point-to-point (PTP) and publish/subscribe (pub/sub).D: As per the “Message Delivery Mode” section of the JMS Specification, messages can be specified as persistent or non-persistent.Reference: http://docs.oracle.com/cd/E12840_01/wls/docs103/jms/fund.html